fix(typing): drain 6 more modules (exempt list 26 -> 20, 79 of 99 checked) - #98

…OMMAND (#100)

`local_verify.verify()` ran `test_cmd` twice -- once in the worktree, once against
the extracted base -- and returned ONE verdict from `red["ok"]`. `red["ok"]` goes
False as soon as ANY test in the command fails against the base, so ONE genuinely
discriminating test earned a PASS for every tautology sitting beside it in the same
file, and named none of them. Hit for real: a three-test file where 2 of 3 were
tautologies returned a bare PASS (Fine-Art-Archive audit finding F3).

`_analyse_nodes` re-runs the candidate paths ALONE against the same extracted base
with `pytest -v --tb=no` and reads the per-node outcomes: FAILED/ERROR
`discriminates`, PASSED `hollow` (named by node id), SKIPPED/XFAIL/XPASS
`inconclusive`. ONE extra subprocess, not one per node, sharing the caller's
`timeout`. The result gains `hollow_nodes`, `node_verdict` and
`node_analysis.counts`.

ADVISORY BY CONSTRUCTION. `verdict`, `ok` and the CLI exit code keep their exact
meaning, so `runtime_ac`, `synthesis_promotion` and `record_verdict` read what they
always read. The finding travels on `reason`, which is what `record_verdict` writes
to `outcomes.notes`, and node ids go into the completion event's `test_ids` -- the
only test-identity field the payload schema has, since an extra key is REJECTED by
`feedback._sanitize_completion_payload`.

Scoping the probe to `test_paths` rather than the whole `test_cmd` tightens the
evidence a second way: a failure in some unrelated test the command happens to run
can no longer read as this change's proof.

WHEN IT CANNOT ATTRIBUTE IT SAYS SO, with the prerequisite NAMED -- no pytest, a
collection error, non-Python paths, a timeout -- and a PASS carrying an
INDETERMINATE analysis appends that to its own reason. An empty hollow list and
"could not look" read identically otherwise, which is the masking this change
exists to remove.

Two under-reporting traps closed, each proven by break->revert:
- the probe parses UNTRUNCATED stdout. `_run`'s 4000-char tail drops the earliest
  nodes of any sizeable file.
- the probe clears inherited `PYTEST_ADDOPTS`. `-x` stops at the first failing node
  -> false clean `node_verdict: PASS` with zero hollow nodes; `-n auto` activates
  xdist, whose verbose lines put the outcome BEFORE the node id -> nothing parses.
  Both measured with the guard removed.

DEDUP (CLAUDE.md 0): hollow detection exists twice, both at coarser grain --
`local_verify.verify` per COMMAND and `objective_anchor.arm_signals` per ARM
(base_pass boolean) -- and `testgen_gate.pytest_cmd(collect_only=True)` builds a
pytest collection command but reads only `ok`. No per-node parser or attribution
exists anywhere in the tree. The improvement log records this precision limit as
STILL OPEN; extended `local_verify` rather than building anything new, and the
`deliberate-break-verifier` capability's lifecycle state is unchanged.

Selftest adds the mixed real+tautology fixture on the existing `_init_repo`, with a
DELIBERATE BREAK -> REVERT on `NODE_OUTCOME_DISPOSITIONS`: count a base-passing node
as part of the proof and the run reverts to exactly the old masking PASS. Also pins
the two parse shapes that would under-report (an outcome word inside a summary error
message; xdist's outcome-first line) and the named-prerequisite INDETERMINATE path.
It needs only git and pytest, so it runs on a bare runner -- NO ceiling moved and
nothing new is skipped.

NO FLOOR CHANGE, and that is measured not assumed: the new coverage is in the module
selftest, so pytest collects the same 442. Re-measured on the merge result after
rebasing onto origin/main 146b458 (#98 and #91 landed underneath): 442 passed / 442
collected / floor 442, 85/85 selftests, 5/5 gates, mypy ratchet 20/20 unchanged and
`local_verify` stays off the exempt list.

Deliberately NOT recorded as a `capability_propensity.record_repair`: the
`deliberate-break-verifier` repair proposal was drained on 2026-08-23 for the
unrelated NO_BINDING-surface defect in PR #32, and this precision limit was never in
that proposal's defect evidence. Recorded as its own finding on improvement-log
item 0 instead.

Co-authored-by: Tim Stranske <tim@stranskemo.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>